Thanks everyone. Of course I see now that writing a single file with all of
the camera vectors in a single file and having POV-Ray #read each frame is a
much better way to do it. Can anyone point me to a simple working example of
this type of I/O? I looked at the documentation, but I am still a little
fuzzy.

Thanks
"ingo" <ing### [at] tagpovrayorg> wrote in message
news:Xns### [at] netplexaussieorg...
> in news:3f9d95e5$1@news.povray.org Todd Haygood wrote:
>
> > I have written a freehand camera path drawing program in Visual Basic
> > 6. I am sure there is a better way to do what I am doing without
> > generating lots of POVRAY files, but I just wanted to make it work.
> > My program does work quite well, but having to reload the filequeue
> > in 512 chunks is a bit of a pain.
>
> As your program seems to generate POV files, you can probably modify
> your program in such a way that, instead of writing each file to disk,
> it calls POV-Ray for each frame and passes the 'file' through stdout.
> Gilles Tran somewhere posted how he calls POV-Ray from VBA (Access).
>
> Another way could be that, for every frame, your program writes an
> include file that contains the camera statement.
> You need a, single, scene file that has to include the right camera
> include file for each consecutive frame. Check 'frame_number' in
> "6.1.3.4.2  Clock Identifiers" for how to control this.
>
> > Is there any way to set the Max Value of the filequeue short of
> > re-compiling?
>
> No.
>
> Ingo

Post a reply to this message